Skip to content

docs: fix stable release runbook timing - #43

Merged
tensornull merged 1 commit into
mainfrom
agent/fix-release-runbook-timing
Jul 30, 2026
Merged

docs: fix stable release runbook timing#43
tensornull merged 1 commit into
mainfrom
agent/fix-release-runbook-timing

Conversation

@tensornull

Copy link
Copy Markdown
Contributor

Summary

  • place the final releasable-doc validation on the generated four-file Release Please PR head, after the preceding implementation/finalization PR lands the documentation transition
  • freeze new Release Please workflows and unrelated reruns from the release-PR merge through registry verification and final state readback
  • retain only the already bounded source-run retry and same-run Release reconciliation exceptions

Why

The post-release documentation PR correctly separated the four-file generated release PR from preceding public-status edits, but the adjacent validation command could still be read as running before the package version bump. It also started the Release Please run-set freeze too late, leaving a race between the release-PR merge and tag handoff.

Validation

  • clean exact-HEAD npm run verify (477 tests and complete package/workflow/standalone gates)
  • 397 targeted release/workflow contract tests in independent adversarial review
  • npm run format:check
  • npm run check:public-preview
  • npm run actionlint
  • git diff --check

@tensornull
tensornull marked this pull request as ready for review July 30, 2026 12:22

@tensornull tensornull left a comment

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Owner exact-head audit completed for 7d8d79d after all required CI passed. This COMMENTED review records the audit under the zero-required-approval ruleset; it is not an APPROVED review because the reviewer and PR author are the same account.

@tensornull
tensornull merged commit 66c8a80 into main Jul 30, 2026
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant